Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Gh actions addition #9

Closed
wants to merge 25 commits into from
Closed

Gh actions addition #9

wants to merge 25 commits into from

Conversation

oneanupam
Copy link
Owner

Description

Please include a short summary of the update made along with the context.

Checklist

  • Self-review of the code is performed.
  • Code has been fully tested and completely functional.

Type of Change

  • break: Resolved a breaking change. This will increment the major version.
  • feat: A new feature or enhancement added to the codebase. This will increment the minor version.
  • fix: A bug fix or correction to resolve an issue. This will increment the patch version.
  • chore: Other changes not directly affecting the code (e.g., documentation update). No version increment.

Reference

https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/creating-a-pull-request-template-for-your-repository

@github-actions GitHub Actions
Copy link

Terraform Format and Style 🖌success

Terraform Initialization ⚙️success

Terraform Validation 🤖success

Validation Output 

Success! The configuration is valid.

Terraform Plan 📖success

Show Plan 

terraform

Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # google_compute_network.tst_vpc will be created
  + resource "google_compute_network" "tst_vpc" {
      + auto_create_subnetworks                   = false
      + delete_default_routes_on_create           = false
      + description                               = "The foundation vpc network."
      + gateway_ipv4                              = (known after apply)
      + id                                        = (known after apply)
      + internal_ipv6_range                       = (known after apply)
      + mtu                                       = (known after apply)
      + name                                      = "fdn-tst-vpc-01"
      + network_firewall_policy_enforcement_order = "AFTER_CLASSIC_FIREWALL"
      + numeric_id                                = (known after apply)
      + project                                   = "tidy-interface-421310"
      + routing_mode                              = "GLOBAL"
      + self_link                                 = (known after apply)
    }

Plan: 1 to add, 0 to change, 0 to destroy.

─────────────────────────────────────────────────────────────────────────────

Note: You didn't use the -out option to save this plan, so Terraform can't
guarantee to take exactly these actions if you run "terraform apply" now.

Pusher: @anupam-sy, Action: pull_request, Working Directory: ``, Workflow: Terraform GitHub Actions

@github-actions GitHub Actions
Copy link

Terraform Format and Style 🖌success

Terraform Initialization ⚙️success

Terraform Validation 🤖success

Validation Output 

Success! The configuration is valid.

Terraform Plan 📖success

Show Plan 

terraform

Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # google_compute_network.tst_vpc will be created
  + resource "google_compute_network" "tst_vpc" {
      + auto_create_subnetworks                   = false
      + delete_default_routes_on_create           = false
      + description                               = "The foundation vpc network."
      + gateway_ipv4                              = (known after apply)
      + id                                        = (known after apply)
      + internal_ipv6_range                       = (known after apply)
      + mtu                                       = (known after apply)
      + name                                      = "fdn-tst-vpc-01"
      + network_firewall_policy_enforcement_order = "AFTER_CLASSIC_FIREWALL"
      + numeric_id                                = (known after apply)
      + project                                   = "tidy-interface-421310"
      + routing_mode                              = "GLOBAL"
      + self_link                                 = (known after apply)
    }

Plan: 1 to add, 0 to change, 0 to destroy.

─────────────────────────────────────────────────────────────────────────────

Note: You didn't use the -out option to save this plan, so Terraform can't
guarantee to take exactly these actions if you run "terraform apply" now.

Pusher: @anupam-sy, Action: pull_request, Working Directory: ``, Workflow: GitOps Implementation

@github-actions GitHub Actions
Copy link

Terraform Format and Style 🖌success

Terraform Initialization ⚙️success

Terraform Validation 🤖success

Validation Output 

Success! The configuration is valid.

Terraform Plan 📖success

Show Plan 

terraform

Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # google_compute_network.tst_vpc will be created
  + resource "google_compute_network" "tst_vpc" {
      + auto_create_subnetworks                   = false
      + delete_default_routes_on_create           = false
      + description                               = "The foundation vpc network."
      + gateway_ipv4                              = (known after apply)
      + id                                        = (known after apply)
      + internal_ipv6_range                       = (known after apply)
      + mtu                                       = (known after apply)
      + name                                      = "fdn-tst-vpc-01"
      + network_firewall_policy_enforcement_order = "AFTER_CLASSIC_FIREWALL"
      + numeric_id                                = (known after apply)
      + project                                   = "tidy-interface-421310"
      + routing_mode                              = "GLOBAL"
      + self_link                                 = (known after apply)
    }

Plan: 1 to add, 0 to change, 0 to destroy.

─────────────────────────────────────────────────────────────────────────────

Note: You didn't use the -out option to save this plan, so Terraform can't
guarantee to take exactly these actions if you run "terraform apply" now.

Pusher: @anupam-sy, Action: pull_request, Working Directory: ``, Workflow: GitOps Implementation

@github-actions GitHub Actions
Copy link

Terraform Format and Style 🖌``

Terraform Initialization ⚙️``

Terraform Validation 🤖``

Validation Output

Terraform Plan 📖``

Show Plan 

terraform

Pusher: @anupam-sy, Action: pull_request, Working Directory: ``, Workflow: GitOps Implementation

@github-actions GitHub Actions
Copy link

Terraform Format and Style 🖌``

Terraform Initialization ⚙️``

Terraform Validation 🤖``

Validation Output

Terraform Plan 📖``

Show Plan 

terraform

Pusher: @anupam-sy, Action: pull_request, Working Directory: ``, Workflow: GitOps Implementation

@github-actions GitHub Actions
Copy link

Terraform Format and Style 🖌``

Terraform Initialization ⚙️``

Terraform Validation 🤖``

Validation Output

Terraform Plan 📖``

Show Plan 

terraform

Pusher: @anupam-sy, Action: pull_request, Working Directory: ``, Workflow: GitOps Implementation

1 similar comment
@github-actions GitHub Actions
Copy link

Terraform Format and Style 🖌``

Terraform Initialization ⚙️``

Terraform Validation 🤖``

Validation Output

Terraform Plan 📖``

Show Plan 

terraform

Pusher: @anupam-sy, Action: pull_request, Working Directory: ``, Workflow: GitOps Implementation

@oneanupam oneanupam closed this Jun 14, 2024
@oneanupam oneanupam deleted the gh-actions-addition branch June 14, 2024 23:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@oneanupam